-
Notifications
You must be signed in to change notification settings - Fork 52
RHIDP-5152: Add Frontend Plugn Wiring Section #1259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
RHIDP-5152: Add Frontend Plugn Wiring Section #1259
Conversation
Updated preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1259/ @ 08/12/25 16:59:22 |
2446db4
to
76d0e47
Compare
modules/dynamic-plugins/proc-extending-internal-icon-catalog.adoc
Outdated
Show resolved
Hide resolved
modules/dynamic-plugins/proc-customizing-sidebar-menu-items.adoc
Outdated
Show resolved
Hide resolved
There's also a couple more sections worth mentioning:
apologies if I missed those, I'm still looking through this. |
76d0e47
to
bbf271f
Compare
@gashcrumb, Please have a look at this PR. I have made some changes to incorporate the following sections:
|
* Declare a new full page by defining a new route | ||
* Extend to an existing page using router bindings | ||
* Use mount points within the application | ||
* Provide additional utility APIs or replace existing ones |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure is it worth adding mention of the SignInPage, scaffolder or techdocs extensions etc in this list? This seems like a high-level overview of features, so maybe it doesn't need to be an exhaustive list I guess.
* `/context` type that serves to create React contexts | ||
* `/cards` type for regular React components | ||
|
||
The following is an example of the overall configuration structure of a mount point: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if this section that focuses on mount points would be better in the "using mount points section", as they're used across the app, whereas entity tabs are limited to only catalog items. I was just reminded too that the conditional viewing of a component is done as part of the mount point configuration, which could almost warrant it's own section as there's a few conditional functions that are available and we probably could go into a little more detail on what's possible with the conditional functions for mount points.,
[source,yaml] | ||
---- | ||
import { lightTheme } from './lightTheme'; | ||
import { darkTheme } from './darkTheme'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be worth linking to here for folks wondering how to create these?
7d5bbe5
to
53aa209
Compare
Add frontend plugn wiring section
53aa209
to
6aecf36
Compare
IMPORTANT: Do Not Merge - To be merged by Docs Team Only
Version(s): 1.6, 1.7, main
Issue: RHIDP-5152
Preview:
5. Frontend plugin wiring
5.1. Extending internal icon catalog
5.2. Defining dynamic routes for new plugin pages
5.3. Customizing menu items in the sidebar navigation
5.4. Binding to existing plugins
5.5. Using mount points
5.6. Customizing and extending entity tabs
5.7. Provide additional utility APIs
5.8. Adding custom authentication provider settings
5.9. Provide custom TechDocs addons
5.10. Customizing Red Hat Developer Hub theme